feat: add any and list type in the CustomFieldValidation#76
Merged
Conversation
- Add FieldType literal union and named validation option interfaces - Make CustomApiFieldBase a discriminated union on field_type - Export getCommonValidation() helper for accessing common props - Export getValidationFor() helper for type-safe field-specific access Enables type-safe validation access after narrowing field_type.
ellanan
changed the title
any and list type in the CustomFieldValidation
field123
approved these changes
Feb 3, 2026
|
🎉 This PR is included in version 31.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Type
Feature
Implements a new featureDescription
anyandlisttype in the CustomFieldValidationDependencies